provider Events PUT /api/0/projects/{organization_id_or_slug}/{project_id_or_slug}/issues/
@utdk/sentry /api/0/projects/{organization_id_or_slug}/{project_id_or_slug}/issues/
Bulk Mutate a List of Issues
Bulk mutate various attributes on issues. The list of issues to modify is given through the `id` query parameter. It is repeated for each issue that should be modified. - For non-status updates, the `id` query parameter is required. - For status updates, the `id` query parameter may be omitted for a batch "update all" query. - An optional `status` query parameter may be used to restrict mutations to only events with the given status. The following attributes can be modified and are supplied as JSON object in the body: If any IDs are out of scope this operation will succeed without any data mutation.
organization_id_or_slug path required
The ID or slug of the organization the issues belong to.
string
project_id_or_slug path required
The ID or slug of the project the issues belong to.
string
id query
A list of IDs of the issues to be mutated. This parameter shall be repeated for each issue. It is optional only if a status is mutated in which case an implicit update all is assumed.
integer
status query
Optionally limits the query to issues of the specified status. Valid values are `"resolved"`, `"reprocessing"`, `"unresolved"`, and `"ignored"`.
string

Try it

Authentication
Configure credentials for API Reference
Gateway
The gateway proxies requests and injects credentials server-side. Configure credentials above, then enter your gateway URL.

Saved automatically to browser storage.

bulkMutateAListOfIssues
PUT/api/0/projects/{organization_id_or_slug}/{project_id_or_slug}/issues/
Bulk mutate various attributes on issues. The list of issues to modify is given through the `id` query parameter. It is repeated for each issue that should be modified. - For non-status updates, the `id` query parameter is required. - For status updates, the `id` query parameter may be omitted for a batch "update all" query. - An optional `status` query parameter may be used to restrict mutations to only events with the given status. The following attributes can be modified and are supplied as JSON object in the body: If any IDs are out of scope this operation will succeed without any data mutation.

Parameters

required

The ID or slug of the organization the issues belong to.

required

The ID or slug of the project the issues belong to.

A list of IDs of the issues to be mutated. This parameter shall be repeated for each issue. It is optional only if a status is mutated in which case an implicit update all is assumed.

Optionally limits the query to issues of the specified status. Valid values are `"resolved"`, `"reprocessing"`, `"unresolved"`, and `"ignored"`.

Input

The new status for the issues. Valid values are `"resolved"`, `"resolvedInNextRelease"`, `"unresolved"`, and `"ignored"`.

Additional details about the resolution. Valid values are `"inRelease"`, `"inNextRelease"`, `"inCommit"`, `"ignoreDuration"`, `"ignoreCount"`, `"ignoreWindow"`, `"ignoreUserCount"`, and `"ignoreUserWindow"`.

The number of minutes to ignore this issue.

Sets the issue to public or private.

Allows to merge or unmerge different issues.

The actor ID (or username) of the user or team that should be assigned to this issue.

In case this API call is invoked with a user context this allows changing of the flag that indicates if the user has seen the event.

In case this API call is invoked with a user context this allows changing of the bookmark flag.

Enter a gateway URL above to enable sending.

Code snippet
Updates live as you fill in the form above.

TypeScript

import sentry from '@utdk/sentry';

await sentry.bulkMutateAListOfIssues()